Skip to content

feat!(tools/looker): Factor Looker LookML development tools into their own prebuilt config#2559

Merged
drstrangelooker merged 1 commit intomainfrom
looker-dev-prebuilt
Feb 27, 2026
Merged

feat!(tools/looker): Factor Looker LookML development tools into their own prebuilt config#2559
drstrangelooker merged 1 commit intomainfrom
looker-dev-prebuilt

Conversation

@drstrangelooker
Copy link
Copy Markdown
Contributor

Description

In order to reduce the bloat of tools, users who do not need LookML development tools can use --prebuilt looker, while users that need the full suite of tools can use --prebuilt looker,looker-dev

PR Checklist

Thank you for opening a Pull Request! Before submitting your PR, there are a
few things you can do to make sure it goes smoothly:

  • Make sure you reviewed
    CONTRIBUTING.md
  • Make sure to open an issue as a
    bug/issue
    before writing your code! That way we can discuss the change, evaluate
    designs, and agree on the general idea
  • Ensure the tests and linter pass
  • Code coverage does not decrease (if any source code was changed)
  • Appropriate docs were updated (if necessary)
  • Make sure to add ! if this involve a breaking change

@drstrangelooker drstrangelooker requested a review from a team as a code owner February 24, 2026 20:36
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @drstrangelooker, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refactors the Looker tool configurations by separating LookML development-specific tools into a new, dedicated prebuilt configuration named looker-dev. This change aims to reduce the default toolset bloat for users who only require core Looker functionalities, while still providing access to the full suite of development tools for those who need them.

Highlights

  • New looker-dev Prebuilt Configuration: A dedicated prebuilt configuration named looker-dev has been introduced to house LookML development-specific tools.
  • Refactored looker Prebuilt Configuration: The existing looker prebuilt configuration has been streamlined to include only core Looker functionalities, with development tools moved to looker-dev.
  • Flexible Tool Selection: Users can now choose to load only core Looker tools using --prebuilt looker or include the full suite of development tools by specifying --prebuilt looker,looker-dev.
  • Updated Documentation: The reference documentation has been updated to detail the new looker-dev prebuilt configuration, including its tools, environment variables, and permissions.
Changelog
  • cmd/internal/tools_file_test.go
    • Added a new test case for the looker-dev prebuilt configuration.
    • Updated the existing looker prebuilt configuration test case to reflect the reduced set of tools.
  • docs/en/reference/prebuilt-tools.md
    • Added a new section detailing the Looker Dev prebuilt configuration, including its --prebuilt value, environment variables, permissions, and the list of tools it provides.
  • internal/prebuiltconfigs/tools/looker-dev.yaml
    • Created a new YAML file defining the looker-dev prebuilt configuration, which includes a looker-dev-source and a looker_dev_tools toolset containing all LookML development-related tools.
  • internal/prebuiltconfigs/tools/looker.yaml
    • Removed all LookML development-related tools from the tools section and the looker_tools toolset, leaving only the core Looker tools.
Activity
  • Reviewed CONTRIBUTING.md.
  • Ensured tests and linter passed.
  • Verified code coverage did not decrease.
  • Updated appropriate documentation.
  • Marked the change as breaking.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request successfully factors LookML development tools into their own prebuilt configuration, enhancing modularity and allowing users to select specific toolsets based on their needs. The changes are well-implemented across the configuration files, documentation, and tests, with a minor suggestion for improving test code readability.

Comment thread cmd/internal/tools_file_test.go Outdated
@github-actions
Copy link
Copy Markdown
Contributor

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions
Copy link
Copy Markdown
Contributor

@drstrangelooker drstrangelooker enabled auto-merge (squash) February 27, 2026 21:34
@drstrangelooker drstrangelooker merged commit f479475 into main Feb 27, 2026
24 checks passed
@drstrangelooker drstrangelooker deleted the looker-dev-prebuilt branch February 27, 2026 21:59
@github-actions
Copy link
Copy Markdown
Contributor

🧨 Preview deployments removed.

github-actions Bot pushed a commit that referenced this pull request Feb 27, 2026
…nto their own prebuilt config (#2559)

## Description

In order to reduce the bloat of tools, users who do not need LookML
development tools can use `--prebuilt looker`, while users that need the
full suite of tools can use `--prebuilt looker,looker-dev`

## PR Checklist

> Thank you for opening a Pull Request! Before submitting your PR, there
are a
> few things you can do to make sure it goes smoothly:

- [x] Make sure you reviewed

[CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md)
- [ ] Make sure to open an issue as a

[bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose)
  before writing your code! That way we can discuss the change, evaluate
  designs, and agree on the general idea
- [x] Ensure the tests and linter pass
- [x] Code coverage does not decrease (if any source code was changed)
- [x] Appropriate docs were updated (if necessary)
- [x] Make sure to add `!` if this involve a breaking change f479475
github-actions Bot pushed a commit to renovate-bot/googleapis-_-genai-toolbox that referenced this pull request Feb 27, 2026
…nto their own prebuilt config (googleapis#2559)

## Description

In order to reduce the bloat of tools, users who do not need LookML
development tools can use `--prebuilt looker`, while users that need the
full suite of tools can use `--prebuilt looker,looker-dev`

## PR Checklist

> Thank you for opening a Pull Request! Before submitting your PR, there
are a
> few things you can do to make sure it goes smoothly:

- [x] Make sure you reviewed

[CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md)
- [ ] Make sure to open an issue as a

[bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose)
  before writing your code! That way we can discuss the change, evaluate
  designs, and agree on the general idea
- [x] Ensure the tests and linter pass
- [x] Code coverage does not decrease (if any source code was changed)
- [x] Appropriate docs were updated (if necessary)
- [x] Make sure to add `!` if this involve a breaking change f479475
github-actions Bot pushed a commit to Jaleel-zhu/genai-toolbox that referenced this pull request Feb 27, 2026
…nto their own prebuilt config (googleapis#2559)

## Description

In order to reduce the bloat of tools, users who do not need LookML
development tools can use `--prebuilt looker`, while users that need the
full suite of tools can use `--prebuilt looker,looker-dev`

## PR Checklist

> Thank you for opening a Pull Request! Before submitting your PR, there
are a
> few things you can do to make sure it goes smoothly:

- [x] Make sure you reviewed

[CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md)
- [ ] Make sure to open an issue as a

[bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose)
  before writing your code! That way we can discuss the change, evaluate
  designs, and agree on the general idea
- [x] Ensure the tests and linter pass
- [x] Code coverage does not decrease (if any source code was changed)
- [x] Appropriate docs were updated (if necessary)
- [x] Make sure to add `!` if this involve a breaking change f479475
github-actions Bot pushed a commit to pepe57/genai-toolbox that referenced this pull request Feb 28, 2026
…nto their own prebuilt config (googleapis#2559)

## Description

In order to reduce the bloat of tools, users who do not need LookML
development tools can use `--prebuilt looker`, while users that need the
full suite of tools can use `--prebuilt looker,looker-dev`

## PR Checklist

> Thank you for opening a Pull Request! Before submitting your PR, there
are a
> few things you can do to make sure it goes smoothly:

- [x] Make sure you reviewed

[CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md)
- [ ] Make sure to open an issue as a

[bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose)
  before writing your code! That way we can discuss the change, evaluate
  designs, and agree on the general idea
- [x] Ensure the tests and linter pass
- [x] Code coverage does not decrease (if any source code was changed)
- [x] Appropriate docs were updated (if necessary)
- [x] Make sure to add `!` if this involve a breaking change f479475
github-actions Bot pushed a commit to xaas-cloud/genai-toolbox that referenced this pull request Feb 28, 2026
…nto their own prebuilt config (googleapis#2559)

## Description

In order to reduce the bloat of tools, users who do not need LookML
development tools can use `--prebuilt looker`, while users that need the
full suite of tools can use `--prebuilt looker,looker-dev`

## PR Checklist

> Thank you for opening a Pull Request! Before submitting your PR, there
are a
> few things you can do to make sure it goes smoothly:

- [x] Make sure you reviewed

[CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md)
- [ ] Make sure to open an issue as a

[bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose)
  before writing your code! That way we can discuss the change, evaluate
  designs, and agree on the general idea
- [x] Ensure the tests and linter pass
- [x] Code coverage does not decrease (if any source code was changed)
- [x] Appropriate docs were updated (if necessary)
- [x] Make sure to add `!` if this involve a breaking change f479475
AjmeraParth132 pushed a commit to AjmeraParth132/genai-toolbox that referenced this pull request Mar 2, 2026
…r own prebuilt config (googleapis#2559)

## Description

In order to reduce the bloat of tools, users who do not need LookML
development tools can use `--prebuilt looker`, while users that need the
full suite of tools can use `--prebuilt looker,looker-dev`

## PR Checklist

> Thank you for opening a Pull Request! Before submitting your PR, there
are a
> few things you can do to make sure it goes smoothly:

- [x] Make sure you reviewed

[CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md)
- [ ] Make sure to open an issue as a

[bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose)
  before writing your code! That way we can discuss the change, evaluate
  designs, and agree on the general idea
- [x] Ensure the tests and linter pass
- [x] Code coverage does not decrease (if any source code was changed)
- [x] Appropriate docs were updated (if necessary)
- [x] Make sure to add `!` if this involve a breaking change
NirajNandre pushed a commit to NirajNandre/genai-toolbox-fork that referenced this pull request Mar 24, 2026
…r own prebuilt config (googleapis#2559)

## Description

In order to reduce the bloat of tools, users who do not need LookML
development tools can use `--prebuilt looker`, while users that need the
full suite of tools can use `--prebuilt looker,looker-dev`

## PR Checklist

> Thank you for opening a Pull Request! Before submitting your PR, there
are a
> few things you can do to make sure it goes smoothly:

- [x] Make sure you reviewed

[CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md)
- [ ] Make sure to open an issue as a

[bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose)
  before writing your code! That way we can discuss the change, evaluate
  designs, and agree on the general idea
- [x] Ensure the tests and linter pass
- [x] Code coverage does not decrease (if any source code was changed)
- [x] Appropriate docs were updated (if necessary)
- [x] Make sure to add `!` if this involve a breaking change
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants